Skip to content

Conversation

github-actions[bot]
Copy link
Contributor

Backport ebc7e4d from #13357 to 2.21.

We prevent an exception from occurring when trying to remove a probe that did not resolve to a valid source code location.

Checklist

  • PR author has checked that all the criteria below are met
  • The PR description includes an overview of the change
  • The PR description articulates the motivation for the change
  • The change includes tests OR the PR description describes a testing strategy
  • The PR description notes risks associated with the change, if any
  • Newly-added code is easy to change
  • The change follows the library release note guidelines
  • The change includes or references documentation updates if necessary
  • Backport labels are set (if applicable)

Reviewer Checklist

  • Reviewer has checked that all the criteria below are met
  • Title is accurate
  • All changes are related to the pull request's stated goal
  • Avoids breaking API changes
  • Testing strategy adequately addresses listed risks
  • Newly-added code is easy to change
  • Release note makes sense to a user of the library
  • If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
  • Backport labels are set in a manner that is consistent with the release branch maintenance policy

@github-actions github-actions bot added the Dynamic Instrumentation Dynamic Instrumentation/Live Debugger label May 12, 2025
@github-actions github-actions bot requested review from a team as code owners May 12, 2025 13:55
@github-actions github-actions bot requested review from avara1986 and taegyunkim May 12, 2025 13:55
@github-actions github-actions bot added the Dynamic Instrumentation Dynamic Instrumentation/Live Debugger label May 12, 2025
@P403n1x87 P403n1x87 closed this May 12, 2025
@P403n1x87 P403n1x87 reopened this May 12, 2025
@P403n1x87 P403n1x87 enabled auto-merge (squash) May 12, 2025 14:11
Copy link
Contributor Author

CODEOWNERS have been resolved as:

releasenotes/notes/fix-unresolved-pending-probe-removal-80fbf85a9c068122.yaml  @DataDog/apm-python
ddtrace/debugging/_probe/registry.py                                    @DataDog/debugger-python
tests/debugging/probe/test_registry.py                                  @DataDog/debugger-python

@pr-commenter
Copy link

pr-commenter bot commented May 12, 2025

Benchmarks

Benchmark execution time: 2025-06-23 19:54:14

Comparing candidate commit 44c77e3 in PR branch backport-13357-to-2.21 with baseline commit 89e8597 in branch 2.21.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 344 metrics, 2 unstable metrics.

@datadog-datadog-prod-us1
Copy link
Contributor

datadog-datadog-prod-us1 bot commented May 15, 2025

No data reported at this time.
This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 82fffbb | Was this helpful? Give us feedback!

We prevent an exception from occurring when trying to remove a probe
that did not resolve to a valid source code location.

## Checklist
- [x] PR author has checked that all the criteria below are met
- The PR description includes an overview of the change
- The PR description articulates the motivation for the change
- The change includes tests OR the PR description describes a testing
strategy
- The PR description notes risks associated with the change, if any
- Newly-added code is easy to change
- The change follows the [library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
- The change includes or references documentation updates if necessary
- Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist
- [ ] Reviewer has checked that all the criteria below are met
- Title is accurate
- All changes are related to the pull request's stated goal
- Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- Testing strategy adequately addresses listed risks
- Newly-added code is easy to change
- Release note makes sense to a user of the library
- If necessary, author has acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment
- Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)

(cherry picked from commit ebc7e4d)
@tylfin tylfin force-pushed the backport-13357-to-2.21 branch from 44c77e3 to 4ece4e4 Compare July 23, 2025 16:30
@P403n1x87 P403n1x87 merged commit 8ecaa16 into 2.21 Jul 23, 2025
343 checks passed
@P403n1x87 P403n1x87 deleted the backport-13357-to-2.21 branch July 23, 2025 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dynamic Instrumentation Dynamic Instrumentation/Live Debugger
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants